| Package | ForgePatientChart.0830 |
| Type | StructureDefinition |
| Id | Id |
| FHIR Version | R4 |
| Source | https://simplifier.net/resolve?scope=ForgePatientChart.0830@0.1.0&canonical=http://telus.com/fhir/patientChart/StructureDefinition/profile-medication-plan |
| Url | http://telus.com/fhir/patientChart/StructureDefinition/profile-medication-plan |
| Status | draft |
| Name | MedicationPlan |
| Experimental | False |
| Authority | hl7 |
| Type | MedicationRequest |
| Kind | resource |
No resources found
| StructureDefinition | |
http://telus.com/fhir/patientChart/StructureDefinition/ext-medication-request-effective-period  | Ext-Medication Plan Effective Period |
| http://telus.com/fhir/patientChart/StructureDefinition/ext-rendered-dosage-instruction | Ext Rendered Dosage Instruction |
| http://telus.com/fhir/patientChart/StructureDefinition/ext-status-changed | Ext Status Changed Time |
FHIR{
"resourceType" : "StructureDefinition",
"id" : "profile-medication-request-plan-patient-chart",
"url" : "http://telus.com/fhir/patientChart/StructureDefinition/profile-medication-plan",
"name" : "MedicationPlan",
"status" : "draft",
"fhirVersion" : "4.0.1",
"mapping" : [
{
"identity" : "workflow",
"uri" : "http://hl7.org/fhir/workflow",
"name" : "Workflow Pattern"
},
{
"identity" : "script10.6",
"uri" : "http://ncpdp.org/SCRIPT10_6",
"name" : "Mapping to NCPDP SCRIPT 10.6"
},
{
"identity" : "rim",
"uri" : "http://hl7.org/v3",
"name" : "RIM Mapping"
},
{
"identity" : "w5",
"uri" : "http://hl7.org/fhir/fivews",
"name" : "FiveWs Pattern Mapping"
},
{
"identity" : "v2",
"uri" : "http://hl7.org/v2",
"name" : "HL7 v2 Mapping"
}
],
"kind" : "resource",
"abstract" : false,
"type" : "MedicationRequest",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/MedicationRequest",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "MedicationRequest",
"path" : "MedicationRequest",
"comment" : "Usage Note: EMRs may not be capable of importing plans as FHIR; instead they will import and store the key clinical data in a way that aligns with each EMR data structure. \r\n\r\nUsage Note: In general, each version of the EMR medicaiton record will align with a version of the medication plan. The physician will determine if only the current version is shared, or if a historical view of the medication is to be included in the patient chart.\r\n\r\nConformance Rule: If an EMR imports a plan, the original identfiers must be retained and included when the plan is re-exposed. The EMR must also assign its own identifier to the plan\r\n\r\n\r\nReview complete - June"
},
{
"id" : "MedicationRequest.id",
"path" : "MedicationRequest.id",
"comment" : "Usage Notes: This must be a stable id that must be identifcal with each export, so that importing systems will recognize that they already have a plan. Systems can consider developing a hash formula that is based on the medication (CCDD) and the start date of the plan and an internal patient identifier\r\n\r\nThe only time that a resource does not have an id is when it is being submitted to the server using a create operation.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.meta",
"path" : "MedicationRequest.meta",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.meta.versionId",
"path" : "MedicationRequest.meta.versionId",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.meta.lastUpdated",
"path" : "MedicationRequest.meta.lastUpdated",
"comment" : "REVIEW: DO WE WANT AN EXTENSION INSTEAD?\r\nUsage Note: Timestamp reflecting the time the system stored the information that was used to derive this version of the record (non-FHIR). Example: If a record was imported it will be stored in a db within the EMR and though the plan was created at a later date, it is the db date that is used.\r\n\r\nUsage Note: The plan could be derived from multiple records with different dates; the most appropriate date should be exposed, eg perhaps the earliest.RE\r\n\r\nThis value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http.html#read) interaction.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.meta.source",
"path" : "MedicationRequest.meta.source",
"mustSupport" : true
},
{
"id" : "MedicationRequest.meta.profile",
"path" : "MedicationRequest.meta.profile",
"comment" : "Usage: This fixed value is present in the message to allow the FHIR validator to distinguish between Medication Orders and Medication Plans, as they both use Medication Request resources.\r\n\r\n\r\nIt is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.",
"fixedCanonical" : "http://telus.com/fhir/patientChart/StructureDefinition/medication-request-plan",
"mustSupport" : true
},
{
"id" : "MedicationRequest.meta.security",
"path" : "MedicationRequest.meta.security",
"comment" : "Usage: Tags for masked data must be supported. The masked data can be shared with a masked flag. The owner system must ensure that the receiving system adheres to policies. \r\n\r\nThe security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.text",
"path" : "MedicationRequest.text",
"comment" : "Usage Note: Each implementation will deteremine whether this is mandatory. Should be mandatory where possible as receiving systems may not be able to understand all of the discrete data. \r\n\r\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.extension",
"path" : "MedicationRequest.extension",
"slicing" : {
"discriminator" : [
{
"type" : "value",
"path" : "url"
}
],
"rules" : "open"
},
"min" : 0
},
{
"id" : "MedicationRequest.extension:RenderedDosageInstruction",
"path" : "MedicationRequest.extension",
"sliceName" : "RenderedDosageInstruction",
"comment" : "Conformance Rule: This must be populated where applicable and when the dosageInstruction is present. \r\nAlignment: This is a pre-adoption of an R5 element; this is also prsent in PrescribeIT",
"requirements" : "This is the human-readable dosage instruction and therefore must be present whenever possible.",
"min" : 0,
"max" : "1",
"type" : [
{
"code" : "Extension",
"profile" : [
"http://telus.com/fhir/patientChart/StructureDefinition/ext-rendered-dosage-instruction"
]
}
],
"isModifier" : false
},
{
"id" : "MedicationRequest.extension:PlanEffectivePeriod",
"path" : "MedicationRequest.extension",
"sliceName" : "PlanEffectivePeriod",
"min" : 0,
"max" : "1",
"type" : [
{
"code" : "Extension",
"profile" : [
"http://telus.com/fhir/patientChart/StructureDefinition/ext-medication-request-effective-period"
]
}
],
"isModifier" : false
},
{
"id" : "MedicationRequest.extension:StatusChanged",
"path" : "MedicationRequest.extension",
"sliceName" : "StatusChanged",
"definition" : "The date when the status has changed",
"comment" : "This is a pre-adoption of an R5 data element.\r\n https://build.fhir.org/medicationrequest-definitions.html#MedicationRequest.statusChanged",
"min" : 0,
"max" : "1",
"type" : [
{
"code" : "Extension",
"profile" : [
"http://telus.com/fhir/patientChart/StructureDefinition/ext-status-changed"
]
}
],
"isModifier" : false
},
{
"id" : "MedicationRequest.identifier",
"path" : "MedicationRequest.identifier",
"comment" : "Usage: Use of this data element will be determined by each implementation.\r\n\r\nThis is a business identifier, not a resource identifier."
},
{
"id" : "MedicationRequest.status",
"path" : "MedicationRequest.status",
"comment" : "Conformance Rule: In the context of a plan, this may be active, on-hold, stopped or completed. Though a draft plan may exist in the EMR it will not be sent as there is no clinical value in doing so. There is no known use case for \"unknown\" and \"entered in error\" at this time.\r\n\r\nConformance Rule: If the physician has discontinued the medication, prior to the plan naturally completing, the status will be \"stopped\" ; this is an end-state and the status is never moved to \"completed\"\r\n\r\nConformance Rule: if the plan naturally completes (when the medication end date is reached) the status will be \"completed\" and this will have a provenance.activity of \"auto-complete\". If the status is scheduled in advance, (eg by assigning an end-date), the status of \"completed\" will only be exposed after the scheduled event occurs. The end-date will trigger the status change and the provenance associated with this action will indicate an \"auto-complete\" has occurred.\r\n\r\nConformance Rule: If the patient is no longer taking the medication and the source system cannot determine concretely whether the drug was completed or stopped, set value = \"stopped\". If a medication that was not auto-completed/auto-discontinued/auto-ended is no longer being taken then the state = \"stopped\". If the patient is still taking the medicaiton, the state will be active.\r\n\r\n\r\n\r\nConformance Rule: . A short term medication that automatically completed in the past will be sent with a \"completed\" status. \r\n\r\nUsage Note: In the context of sharing medication data, we would not send plans with a status of entered in error, draft or unknown\r\n \r\nUsage Note: If a prescription was given to the patient, but never filled, and this is relevant data to be sharing, this can be recorded as discontinued whereby the discontinue date matches the order date. The accompanying text will provide context as to why the patient did not fill the order.\r\n\r\nBackground Discussion: This cannot be tied to the prescription order dates as the doctor may discontinue/stopped because the patient no longer needs the meds (eg headaches). If \"completed\" this means that youve achieved what you intended, then this becomes fuzzy in cases where there are renewals on the RX that are not fulfilled\r\n\r\n\r\nThis element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.status.extension",
"path" : "MedicationRequest.status.extension",
"slicing" : {
"discriminator" : [
{
"type" : "value",
"path" : "url"
}
],
"rules" : "open"
},
"min" : 1
},
{
"id" : "MedicationRequest.status.extension:StatusDate",
"path" : "MedicationRequest.status.extension",
"sliceName" : "StatusDate",
"definition" : "This is the date that the status changed. By example, if the drug became active on Jan 1, and was on hold Jan 15th, this date reflects the date of the status change. Rationale: A plan may be updated for several reasons; this status date is important clinically and is therefore mandatory.",
"comment" : "Usage Note: This will align with the Provenance Occurence date when the status change has occurred.\r\n\r\nThere can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.",
"min" : 1,
"max" : "1",
"type" : [
{
"code" : "Extension",
"profile" : [
"http://telus.com/fhir/StructureDefinition/ext-status-effective-date"
]
}
]
},
{
"id" : "MedicationRequest.status.extension:StatusDate.url",
"path" : "MedicationRequest.status.extension.url",
"fixedUri" : "http://telus.com/fhir/StructureDefinition/ext-status-effective-date"
},
{
"id" : "MedicationRequest.status.extension:StatusDate.value[x]",
"path" : "MedicationRequest.status.extension.value[x]",
"min" : 1
},
{
"id" : "MedicationRequest.statusReason",
"path" : "MedicationRequest.statusReason",
"comment" : "Usage Note: Status reason may be present for exception status's such as medications that are stopped/discontinued. It is not expected that this will be used for status's such as \"active\" or \"completed. Note: Provenance - extension for comments is also populated with this information\r\n\r\nCore-CA - not supported\r\nMA - capture as text and selection from dropdown with NO CONFIGURATION!!! \r\nPSS - text only if available - discontinue reason, or allergy/intolereance reason\r\nMS - no reason captured :D \r\nCHR - \r\n\r\n\r\nThis is generally only used for \"exception\" statuses such as \"suspended\" or \"cancelled\". The reason why the MedicationRequest was created at all is captured in reasonCode, not here.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.statusReason.coding",
"path" : "MedicationRequest.statusReason.coding",
"max" : "1",
"mustSupport" : true
},
{
"id" : "MedicationRequest.statusReason.coding.system",
"path" : "MedicationRequest.statusReason.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.statusReason.coding.code",
"path" : "MedicationRequest.statusReason.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.statusReason.text",
"path" : "MedicationRequest.statusReason.text",
"mustSupport" : true
},
{
"id" : "MedicationRequest.intent",
"path" : "MedicationRequest.intent",
"comment" : "CA-Core: supported\r\nFixed value for this profile\r\n\r\nIt is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.\r\rAn instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.\r\rThis element is labeled as a modifier because the intent alters when and how the resource is actually applicable.",
"fixedCode" : "plan",
"mustSupport" : true
},
{
"id" : "MedicationRequest.reported[x]",
"path" : "MedicationRequest.reported[x]",
"comment" : "Conformance Rule: The EMRs do not have a mechanism for capturing this data discretely. If the plan has been triggered by a medication statement, then the first version of the plan will be reported, value = \"true\". At this point, the physician owns the plan so all subsequent versions of the plan will be set to \"false\". If the plan was triggered by a medication start in the EMR or by a prescription/medication order, this must always be set to \"false\". \r\n\r\nMapping: supported in CA-Core",
"type" : [
{
"code" : "boolean"
}
],
"mustSupport" : true
},
{
"id" : "MedicationRequest.medication[x]",
"path" : "MedicationRequest.medication[x]",
"comment" : "Usage Note: Where possible, this should be a reference to the Medication resource, rather than just the code as pertinent details may be in the resource.\r\n\r\nIf only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the Medication resource is recommended. For example, if you require form or lot number or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource.",
"type" : [
{
"code" : "CodeableConcept"
},
{
"code" : "Reference",
"aggregation" : [
"bundled"
]
}
],
"mustSupport" : true
},
{
"id" : "MedicationRequest.subject",
"path" : "MedicationRequest.subject",
"type" : [
{
"code" : "Reference",
"targetProfile" : [
"http://hl7.org/fhir/StructureDefinition/Patient"
],
"aggregation" : [
"bundled"
]
}
],
"mustSupport" : true
},
{
"id" : "MedicationRequest.subject.reference",
"path" : "MedicationRequest.subject.reference",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.subject.display",
"path" : "MedicationRequest.subject.display",
"comment" : "Usage Note: This must be populated with the Patient Name. \r\n\r\nThis is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.supportingInformation.reference",
"path" : "MedicationRequest.supportingInformation.reference",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.authoredOn",
"path" : "MedicationRequest.authoredOn",
"comment" : "Conformance Rule: In the context of \"plan\" this is often the date when the first prescription was written. If there is no prescription and there is only a plan this will be the date of the original plan. Often EMRs do not have plans so this will be based on the \"start date\" of the medication as recorded in the EMR. \r\n\r\nConformance Rule: This date will NOT change when new versions of the plan are created. \r\n\r\nCA-Core: supported\r\nPrescribeIT: Date written\r\nPrescribeIT Conformance Rule: Must be either equal to or earlier then the MedicationOrder.dispenseRequest.valididityPeriod.start element.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.requester",
"path" : "MedicationRequest.requester",
"comment" : "Usage: This is the originator of the plan and must be populated when known. This is the prescriber (requestor) on the original medication order. For a plan initiated by a medication statement, this may be left blank.\r\n\r\nCA-Core - suppported\r\nPrescribeIT; May2016 \"Prescriber\"\r\n\r\nReferences SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
"type" : [
{
"code" : "Reference",
"aggregation" : [
"bundled"
]
}
],
"mustSupport" : true
},
{
"id" : "MedicationRequest.requester.reference",
"path" : "MedicationRequest.requester.reference",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.requester.display",
"path" : "MedicationRequest.requester.display",
"comment" : "Usage note: This is the name of the requester. \r\nThis is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.reasonCode",
"path" : "MedicationRequest.reasonCode",
"comment" : "Conformance Rule: When creating the plan version, the reason code must be populated with the latest non-empty indication code from the medication orders. Rationale: This is replicated in the plan, as the export may not include the medication orders. \r\n\r\n\r\n\r\nPrescribeIT: supported, 0..5 with binding to PrescriptionIndicationForUse (20190430)\r\nCA-Core: not supported\r\n\r\n\r\nThis could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.reasonCode.coding",
"path" : "MedicationRequest.reasonCode.coding",
"mustSupport" : true
},
{
"id" : "MedicationRequest.reasonCode.coding.system",
"path" : "MedicationRequest.reasonCode.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.reasonCode.coding.code",
"path" : "MedicationRequest.reasonCode.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.reasonCode.text",
"path" : "MedicationRequest.reasonCode.text",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.note",
"path" : "MedicationRequest.note",
"comment" : "Usage Note: This is used to capture information about the medication plan that is not a status reason (eg discontinue reason) or notes pertaining to the dosageInstruction. Example: Doctor's notes pertainining to a dosage change reason, eg blood pressure getting too low, general note such as \"medication working well\" \r\n\r\nUsage Note: This is not specifically related to the latest activity; it is a running list of notes/time. \r\nConformance Rule:: The addition of a note will generate a new version of the plan\r\n\r\nConformance Rule: Provenance is not always shared; if provenance.reason is populated it must be replicated here.\r\n\r\nConformance Rule: If notes are being populated from multiple entities in the EMR, multiple note instances will be populated. They are exposed as a list of notes rather than concatenated.\r\n\r\nPSS: comment field to capture notes such as where dosage change reason can be recorded\r\n\r\n\r\nFor systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. *Annotations SHOULD NOT* be used to communicate \"modifying\" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).",
"mustSupport" : true
},
{
"id" : "MedicationRequest.note.time",
"path" : "MedicationRequest.note.time",
"mustSupport" : true
},
{
"id" : "MedicationRequest.note.text",
"path" : "MedicationRequest.note.text",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction",
"path" : "MedicationRequest.dosageInstruction",
"comment" : "Conformance Rule: The dosage must be specified where known. The dosage line is mandatory when the source system is the source. The dosage may not be known if the plan was triggered by a medication statement.\r\nUsage: If the sending applicaiton cannot produce the discrete dosage instruction, the RenderedDosageInstruction must be used.\r\n\r\nAlignment:: PrescribeIT has extensions for dosage sequence and instruction relationship; it is handled differently in Patient Chart, FHIR R4\r\n\r\nThere are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, \"Ondansetron 8mg orally or IV twice a day as needed for nausea\" or \"Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting\". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.sequence",
"path" : "MedicationRequest.dosageInstruction.sequence",
"comment" : "Usage Rule: The sequence number is used to convey the relationship between instructions. In PrescribeIT, this maps to the concepts of \"and\" or \"then\" that is used to link instructions together properly.\r\n\r\n32 bit number; for values larger than this, use decimal",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.text",
"path" : "MedicationRequest.dosageInstruction.text",
"comment" : "Usage Note: \"As directed\" is a valid dosage\r\nUsage Note: Where applicable, this follows the same conformance rules as PrescribeIT and represents a textual version of the discrete data.\r\n\r\nConformance Rule: When providing multiple dosage lines this can be expressed individually. All dosage lines (full text content) must be concatenated into MedicationOrder.extension(renderedDosageInstruction).\r\n\r\nUsage Note: This is a string composed of any available discrete MedicationOrder.dosageInstruction child elements such as timing, asNeeded[x], siteCodeableConcept, route, dose[x], rate[x], and maxDosePerPeriod for each repetition sequence line.\r\n\r\nExample: Prednisone; variable dosage instruction, or concurrent instructions (1 pill morning and 1 pill before bed) or sequential dosages (1 pill for 2 days, then 2 pills).Note that FHIR strings SHALL NOT exceed 1MB in size\r\n\r\nNote that FHIR strings SHALL NOT exceed 1MB in size",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.additionalInstruction",
"path" : "MedicationRequest.dosageInstruction.additionalInstruction",
"comment" : "Mapping: CHR - OMD requires that additional instructions are captured separately in the EMR\r\nPSS - two text fields; pharmacy instrucitons and \"other\" \r\n\r\nConformance Rule: When providing an additional instruction at the dosage line level (complex), this should be populated when appropriate.\r\n\r\nUsage Note: This follows the same conformance rules as PrescribeIT as follows:- Usage Note: It may be necessary for the EMR to parse instructions such as QHS (take at bedtime), into two data elements DOSAGE_TIMING_FREQUENCY = once a day and 'at bedtime' would be placed into this field.nformation about administration or preparation of the medication (e.g. \"infuse as rapidly as possibly via intraperitoneal port\" or \"immediately following drug x\") should be populated in dosage.text.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing",
"path" : "MedicationRequest.dosageInstruction.timing",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat",
"path" : "MedicationRequest.dosageInstruction.timing.repeat",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.bounds[x]",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.bounds[x]",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.count",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.count",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.countMax",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.countMax",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.duration",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.duration",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.durationMax",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.durationMax",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.durationUnit",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.durationUnit",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.frequency",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.frequency",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.frequencyMax",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.frequencyMax",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.period",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.period",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.periodMax",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.periodMax",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.timing.repeat.periodUnit",
"path" : "MedicationRequest.dosageInstruction.timing.repeat.periodUnit",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.asNeeded[x]",
"path" : "MedicationRequest.dosageInstruction.asNeeded[x]",
"comment" : "Usage Note: This will follow the same conformance rules as PrescribeIT:\r\nConformance Rule: This is ONLY populated when the medication is prescribed on an as needed (i.e. PRN) basis.\r\nConformance Rule: Set value = true\r\nConformance Rule: When this is specified, it is not acceptable to express the quantity exclusively as a duration/DAYS_SUPPLY. The DOSAGE_QUANTITY must be provided.\r\n\r\nConformance Rule: The CodeableConcept should not be used at this time. If it is present, treat it as though the boolean value is set to true.\r\n\r\nCan express \"as needed\" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated. Or you can express \"as needed\" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be True. If you set the Boolean to False, then the dose is given according to the schedule and is not \"prn\" or \"as needed\".",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.site",
"path" : "MedicationRequest.dosageInstruction.site",
"comment" : "IThis follows the same conformance rule as PrescribeIT:\r\n\r\nConformance Rule: When providing a structured SIG, this should be populated when appropriate. If not structured, this should be part of the SIG (RENDERED_DOSAGE_INSTRUCTION)\r\n\r\nf the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite](extension-bodysite.html). May be a summary code, or a reference to a very precise definition of the location, or both.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.site.coding",
"path" : "MedicationRequest.dosageInstruction.site.coding",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.site.coding.system",
"path" : "MedicationRequest.dosageInstruction.site.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.site.coding.code",
"path" : "MedicationRequest.dosageInstruction.site.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.site.text",
"path" : "MedicationRequest.dosageInstruction.site.text",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.route",
"path" : "MedicationRequest.dosageInstruction.route",
"comment" : "Conformance Rule: Coding should be populated if a code is available. However, text is always required.\r\n\r\nNot all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.route.coding",
"path" : "MedicationRequest.dosageInstruction.route.coding",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.route.coding.system",
"path" : "MedicationRequest.dosageInstruction.route.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.route.coding.code",
"path" : "MedicationRequest.dosageInstruction.route.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.route.coding.display",
"path" : "MedicationRequest.dosageInstruction.route.coding.display",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.route.text",
"path" : "MedicationRequest.dosageInstruction.route.text",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.doseAndRate",
"path" : "MedicationRequest.dosageInstruction.doseAndRate",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.doseAndRate.type.coding",
"path" : "MedicationRequest.dosageInstruction.doseAndRate.type.coding",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.doseAndRate.type.coding.system",
"path" : "MedicationRequest.dosageInstruction.doseAndRate.type.coding.system",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.doseAndRate.type.coding.code",
"path" : "MedicationRequest.dosageInstruction.doseAndRate.type.coding.code",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.doseAndRate.type.coding.display",
"path" : "MedicationRequest.dosageInstruction.doseAndRate.type.coding.display",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.doseAndRate.type.text",
"path" : "MedicationRequest.dosageInstruction.doseAndRate.type.text",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.doseAndRate.dose[x]",
"path" : "MedicationRequest.dosageInstruction.doseAndRate.dose[x]",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.doseAndRate.rate[x]",
"path" : "MedicationRequest.dosageInstruction.doseAndRate.rate[x]",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.maxDosePerPeriod",
"path" : "MedicationRequest.dosageInstruction.maxDosePerPeriod",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.maxDosePerPeriod.numerator",
"path" : "MedicationRequest.dosageInstruction.maxDosePerPeriod.numerator",
"mustSupport" : true
},
{
"id" : "MedicationRequest.dosageInstruction.maxDosePerPeriod.denominator",
"path" : "MedicationRequest.dosageInstruction.maxDosePerPeriod.denominator",
"mustSupport" : true
},
{
"id" : "MedicationRequest.substitution",
"path" : "MedicationRequest.substitution",
"comment" : "Conformance Rule: This must be populated when known\r\n\r\nPrescribeIT mapping: Does not exist in PrescribeIT as a discrete data element",
"mustSupport" : true
},
{
"id" : "MedicationRequest.substitution.allowed[x]",
"path" : "MedicationRequest.substitution.allowed[x]",
"mustSupport" : true
},
{
"id" : "MedicationRequest.substitution.reason",
"path" : "MedicationRequest.substitution.reason",
"mustSupport" : true
},
{
"id" : "MedicationRequest.substitution.reason.coding",
"path" : "MedicationRequest.substitution.reason.coding",
"mustSupport" : true
},
{
"id" : "MedicationRequest.substitution.reason.coding.system",
"path" : "MedicationRequest.substitution.reason.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.substitution.reason.coding.code",
"path" : "MedicationRequest.substitution.reason.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.substitution.reason.text",
"path" : "MedicationRequest.substitution.reason.text",
"mustSupport" : true
},
{
"id" : "MedicationRequest.detectedIssue",
"path" : "MedicationRequest.detectedIssue",
"comment" : "Conformance Rule: The source system must send all drug interaction alerts/DUR \"managements\" that are a component of the medication record; these were not added as part of the medication orders/prescription. Most of the DUR managements will be associated with a prescription, as such this will be rarely used. \r\n\r\nConformance Rule: The managed issue is only applicable to a single version of the plan; it is not carried forward to subsequent versions.\r\n\r\nConformance Rule: If there is a medication order with detected issues, the plan must reference the same detected issue (for the plan version that was triggered by the medication order). \r\n\r\nUsage Note: This is used to convey the action the user took (eg override on a warning). This could also be a drug/allergy alert. \r\nUsage Note: EMRs commonly do not capture detected issues unless there is a mitigation attached. \r\nUsage Note: Some exporting systems are not able to capture managed issue at the plan level; rather they will capture managed issues only at time of prescribing/renewals.\r\n\r\nMapping; PrescribeIT extension\r\n\r\nConformance Rules: \r\n\r\nThis element can include a detected issue that has been identified either by a decision support system or by a clinician and may include information on the steps that were taken to address the issue.",
"mustSupport" : true
},
{
"id" : "MedicationRequest.detectedIssue.reference",
"path" : "MedicationRequest.detectedIssue.reference",
"min" : 1,
"mustSupport" : true
},
{
"id" : "MedicationRequest.eventHistory",
"path" : "MedicationRequest.eventHistory",
"comment" : "Usage Note: This is not used as the provenance will reference the Medication Plan, instead of using this relationship\r\n\r\nThis might not include provenances for all versions of the request – only those deemed “relevant†or important. This SHALL NOT include the provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant†change, it will need to be added as part of a later update. Until then, it can be queried directly as the provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.)."
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.